Identify DOORS client inactive state -DXL

Hello,

Are there any possibilities to check whether the DOORS client is closed or not using DXL. Because I am calling .net exe from DXL file for opening .net form. So, once the client is closed i have to close the .net form.

Thanks in advance
Muthurani
muthurani - Thu Jun 03 01:26:04 EDT 2010

Re: Identify DOORS client inactive state -DXL
Mathias Mamsch - Thu Jun 03 03:28:30 EDT 2010

You can put some DXL code in "finish.dxl" in the lib/dxl directory, which is executed when the client closes and signal the form to close.

To run some code when your DXL script finishes you can use "evalTop_" which will execute after your DXL program has finished.

Maybe you can also check from .NET from a timer if the client executable is still running and close the form.

Just some ideas, Regards, Mathias

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

Re: Identify DOORS client inactive state -DXL
Z_T - Mon Jun 21 03:06:08 EDT 2010

Cool! DXL and .Net is my way of doing things for about a year and loving it.

Here is an idea:
- Expose a constructor or some properties for DOORS version,
- Instanciate a FileSystemWatch for the DOORS.exe (make sure you get the right one base on the provided DOORS version)
- Fire an app closed even to close your .Net form.

Beside the FileSystemWatch, you could also use Process and/or Thread within your .Net.

ZT